home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Patches 1995 March
/
SGI IRIX Patches 1995 Mar.iso
/
relnotes
/
patchSG0000079
/
ch1.z
/
ch1
Wrap
Text File
|
1995-03-10
|
9KB
|
331 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_0_0_7_9__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0000079 to IRIX 5.2.
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all graphics platforms
that support PEX (the same platforms that support native
OpenGL). The software cannot be installed on other
configurations.
1.2 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_0_7_9
This patch contains fixes for the following bugs in IRIX
5.2. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
+o Bug #203361: PEX returns IDs of freed resources
PEX was changed to return the token "PEXAlreadyFreed"
for a resource that has been destroyed.
+o (No bug number) PEX returns garbage for requested
viewport
PEX was changed to initialize the requested viewport,
so that garbage values will not be returned if the
viewport is queried.
+o (No bug number) PEX returns wrong path information
PEX was changed to return an empty path for an idle
renderer, and a path that contains an initial structure
ID of 0 for an active renderer. This conforms with the
PEX 5.1 protocol specification.
+o Bug #203989: PEX structure operations produce bogus
PEXLabelError
Under certain conditions, PEX was unable to find an
existing label in a structure.
+o Bug #207340: PEX incorrectly transforms light positions
PEX was changed to transform light positions by the
current view orientation transformation, but not by the
current modeling transformation; i.e. to treat light
positions as being specified in World Coordinate space.
+o (No bug number) PEX performance tuning
- 2 -
Eliminated redundant clear of the image buffer for PEX
5.0 style clients (clients that use X protocol to clear
the image buffer). Also eliminated redundant disabling
of model clip planes, and made modeling matrix
calculations more efficient.
+o Bug #207343: PEX incorrectly transforms clip planes
specifications
PEX was changed to transform model clip planes by the
inverse transpose of the composite modeling
transformation (instead of by the inverse of the
composite modeling transformation).
+o (No bug number) A more accurate depth cueing method was
implemented
+o (No bug number) Rendering performance for all
primitives was improved
+o Bug #210454: PEX bug rendering quad strip with vertex
color
PEX was changed to correct the method of stepping to
next vertex color pair, and for saving the color of the
second vertex, for pairs of vertices that are culled in
a quadrilateral strip.
+o Bug #183564: threads can hang around after program dies
PEX was changed to allow a main thread cleanup function
to be executed after a rendering thread completes.
This allows PEX to send all protocol replies from the
main thread instead of from the rendering thread. The
code was also changed so that only the main thread
stores changes to the renderer state value. These
changes eliminate the collision that occurred when the
server resets itself while a rendering thread is busy.
+o Bug #218095: PEX structure operations are too slow
A new bucket allocator method was implemented to manage
pools of memory for the structure store.
+o Bug #219664: PEX tristrip causes rendering thread crash
PEX was changed to initialize a variable before it was
referenced.
+o Bug #180260: PEX does not support anti-aliasing
- 3 -
Line anti-aliasing now works, but since it shares the
GL blend mechanism with the DEC multipass transparency
rendering extension, line anti-aliasing and
transparency can't be used at the same time. This
change affects the server only; there is still no
PEXlib API function to turn on line anti-aliasing.
+o Bug #221327: PEX rendering thread can crash on client
termination
An inherent race condition in the design of the X
server caused PEX to try to free a block of memory
twice. A pointer is now checked for NULL before it is
dereferenced.
+o Bug #223490: PEX rendering thread crashes on annotation
text element
PEX was changed to check for a null pointer before
freeing a block of memory.
+o Bug #224855: PEX line picking is too slow
A new, faster line picking algorithm was implemented.
+o Bug #234866: PEX server loops or crashes after
PEXChangePipelineContext call
PEX was changed to allocate the correct amount of
memory to store level curve parameters.
+o Bug #240313 Rendering thread can hang in _sginap()
PEX was changed to correct a bug that made rendering of
certain flavors of quad strip and triangle strip
primitives to cause the rendering thread to hang in a
call to _sginap() waiting for the completion of an
inquiry that will never complete. This only occured on
systems with Reality Engine or Reality Engine II
graphics.
+o (No bug number) Memory leaks
On certain systems it was possible for memory allocated
for a client's graphics context and/or display buffers
to not be freed when the client terminated.
- 4 -
1.3 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_0_0_7_9
This patch release includes these subsystems:
+o patchSG0000079.x_eoe_sw.pex
1.4 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install patches for only the problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch, determine the patches that meet your specific
needs.
Patch software is installed like any other Silicon Graphics
software product. It must be installed from the miniroot.
Follow the instructions in your _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n
_G_u_i_d_e to bring up the miniroot form of the software
installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
- 5 -
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.